Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prohibit wildcard import in pylint #8893

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from

Conversation

zhiltsov-max
Copy link
Contributor

@zhiltsov-max zhiltsov-max commented Dec 31, 2024

Motivation and context

In python, wildcard imports like from x import * can unpredictably pollute namespace with symbols that are not really expected. In most cases it's better to use import x as y to get access to all module symbols. For popular libraries importable contents of modules are typically maintained well, but it requires quite a lot of work. Currently, we don't use wildcard imports for anything in the project and I can't currently think of places where it could really be useful, so I think it's best to just prohibit their use entirely.

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • Chores
    • Updated Pylint configuration to modify linting rules for wildcard imports and logging arguments.
    • Adjusted message settings to enable additional code quality checks.

Copy link
Contributor

coderabbitai bot commented Dec 31, 2024

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request introduces modifications to the .pylintrc configuration file, specifically adjusting Pylint's linting rules. The changes involve enabling the wildcard-import message, which was previously disabled, and activating the logging-too-few-args check. These updates suggest a more stringent approach to code quality by enforcing stricter import and logging practices.

Changes

File Change Summary
.pylintrc - Enabled wildcard-import message
- Removed wildcard-import from disabled list
- Enabled logging-too-few-args message

Poem

🐰 Lint, lint, with rabbit might,
Imports wild, now brought to light!
Logging checks, no args too few,
Code quality shines, crisp and true!
Pylint's rules, now sharp and bright! 🔍


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov-commenter
Copy link

codecov-commenter commented Dec 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.84%. Comparing base (411f8e7) to head (5b9b277).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #8893   +/-   ##
========================================
  Coverage    73.84%   73.84%           
========================================
  Files          412      412           
  Lines        44261    44261           
  Branches      3993     3993           
========================================
  Hits         32686    32686           
  Misses       11575    11575           
Components Coverage Δ
cvat-ui 78.41% <ø> (ø)
cvat-server 69.97% <100.00%> (ø)

@SpecLad
Copy link
Contributor

SpecLad commented Dec 31, 2024

I agree with the policy, but we do have extant uses of wildcard imports in the codebase:

$ rg 'import *' -F -t py --sort=path
cvat/apps/engine/__init__.py
7:from .schema import * # force import of declared symbols

cvat/settings/development.py
5:from .base import *

cvat/settings/email_settings.py
6:from cvat.settings.production import *

cvat/settings/production.py
5:from .base import *

cvat/settings/testing.py
5:from .development import *

cvat/settings/testing_rest.py
5:from cvat.settings.production import *

cvat-sdk/cvat_sdk/models.py
5:from cvat_sdk.api_client.models import *  # pylint: disable=unused-import,redefined-builtin

serverless/pytorch/foolwood/siammask/nuclio/model_handler.py
5:from tools.test import *

tests/python/cli/conftest.py
5:from sdk.fixtures import *  # pylint: disable=unused-import

tests/python/conftest.py
5:from shared.fixtures.data import *
6:from shared.fixtures.init import *
7:from shared.fixtures.util import *

tests/python/sdk/conftest.py
5:from .fixtures import *

Would you mind going through these and fixing/suppressing the warning?

@zhiltsov-max
Copy link
Contributor Author

Ok, it seems that these uses just reexport symbols or do some other technical stuff.

@SpecLad
Copy link
Contributor

SpecLad commented Jan 7, 2025

Ok, it seems that these uses just reexport symbols or do some other technical stuff.

Sure, but you still have to suppress the warning. I'm also pretty sure that the star import in serverless/pytorch/foolwood/siammask/nuclio/model_handler.py isn't necessary, and the one in cvat/apps/engine/__init__.py looks questionable as well.



class ModelHandler:
def __init__(self):
# Setup device
self.device = torch.device('cuda' if torch.cuda.is_available() else 'cpu')
torch.backends.cudnn.benchmark = True
self.device = impl.torch.device('cuda' if impl.torch.cuda.is_available() else 'cpu')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

torch is just PyTorch, so could you import it normally (import torch)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't want to change any logic in this script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants